home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Power Tools 1993 November - Disc 2
/
Power Tools Plus (Disc 2 of 2)(November 1993)(HP).iso
/
hotlines
/
slidehl
/
network
/
script.txt
< prev
Wrap
Text File
|
1992-02-03
|
32KB
|
741 lines
Cooperative Computing Through Open Systems
*******
S01.GAL
*******
..pictureA:\NETWORK\S01.GAL,65535,49151,7,44,13,
The objective of networking is to provide a mechanism for access
and manipulation of information. This information is typically
dispersed across multiple locations, in multiple hosts, made by a
variety of computer vendors.
Information, for design, purchasing, manufacturing, sales and
accounting purposes, needs to be accessed by end users, as well as
by interdependent applications. Resources, such as computing power
and printing facilities must be shareable, scalable, and widely
accessible.
A truly open and cooperative computing system provides transparent
access to this information. In addition, seamless integration of
resources enable end users and applications to share the available
resources.
.PA
Benefits Of Cooperative Computing Through Open Systems
*******
S02.GAL
*******
..pictureA:\NETWORK\S02.GAL,65535,49151,7,44,13,
Numerous benefits are provided by cooperative computing through
open systems, technical as well as financial.
A major benefit is flexibility, the capability to optimize
the use of available resources. Shared resources that are
transparently accessible reduce the overall cost of a system by
limiting the use of duplicated, and often idle, resources.
The basic technology enabling this flexibility is a client/server
architecture. Shared resources are located in servers, dedicated
resources act as clients of the servers. The network provides the
infrastructure supporting the architecture.
Interoperability between clients and servers is guaranteed by
adherence to standards. Common networking protocols enable
transparent communications.
Moves, adds, and changes to the system are handled by scalable
resources. Moving an application to a larger or smaller system,
from a different vendor, implies easy portability of software. This
is enabled by the use of standardized application programming
interfaces (APIs). APIs provide software developers with common
environments for application integration, allowing applications to
be moved from one system to another with minimum effort.
Shared information and resources are beneficial to a business only
if reliably available. A networked system needs careful management
to enhance productivity. Centralized and distributed management
capabilities are part of any open cooperative computing system. An
integrated management system provides geographical, resource, and
applications management, maximizing network uptime.
.PA
Network Investment Protection
*******
S03.GAL
*******
..pictureA:\NETWORK\S03.GAL,65535,49151,7,44,13,
While cooperative computing undoubtedly offers great benefits over
existing environments, there still is a large number of existing
systems installed. These existing systems need to become integrated
with the future networked systems necessary for open, cooperative
computing.
Hewlett-Packard is committed to protecting the investments
previously made, so that today's environment will still be viable
tomorrow.
At the same time, major efforts are under way to rapidly deploy new
technologies, allowing the realization of a truly open, cooperative
computing environment to occur sooner.
.PA
Cooperative Computing Environments
*******
SO4.GAL
*******
..pictureA:\NETWORK\S04.GAL,65535,49151,7,44,13,
There are four key areas of functionality within an open,
cooperative computing environment. Two areas deal with the access
to information, and are primarily supporting transaction oriented,
administrative applications. Two areas deal with decision support
applications for so called "knowledge worker" environments.
Basic connectivity provides terminals and desktop computers with
access to local and remote hosts. Terminal emulation protocols
combined with hubs and DTCs provide the basic building blocks of
the networked environment.
Enhanced connectivity enable access to multiple sources of
distributed data. In a global access environemnt LANs are
geographically extended, multiplying the accessible data and
resources. Clients are no longer limited by physical distances to
the servers. A global access infrastructure is developed,
supported by network and systems management.
Network operating systems integrate desktop computers into a local
area network, making the desktops clients of the server hosts.
Shared resources, such as printers and other peripherals, combine
with standard user interfaces and network operating systems to form
the resource sharing environment.
Cooperating applications require integration of servers. Clients
are applications, as well as end users. An interdependent whole is
developed, allowing processes to communicate by sharing
information, automatically conduct transactions, thus increasing
the power of the networked system. Cooperating applications enable
significant increases in productivity, driving the overall cost of
ownership down.
.PA
Host Access
*******
S05.GAL
*******
..pictureA:\NETWORK\S05.GAL,65535,49151,7,44,13,
In this phase, access to the processing power of local and remote
hosts is the key. Terminals are attached to local servers through
data terminal controllers, remote hosts are linked via modems.
Desktop computers, such as PCs and workstations access hosts
through terminal emulation.
Peripheral resources are centralized, and attached to hosts only.
Access is allowed on a time sharing basis, controlled by the host.
Local processing power exists at the desktop level, but no sharing
of data occurs.
.PA
Host Access Environment
*******
S06.GAL
*******
..pictureA:\NETWORK\S06.GAL,65535,49151,7,44,13,
To the end user, application access is possible, but cumbersome. It
is necessary to know the location of data and applications, as well
as the means of accessing it. Elaborate log-on procedures
predominate, and productivity is highly dependent on the management
of the centralized resources.
A typical application example would be an electronic mail system,
such as HP DeskManager. The application resides on a local or
remote host, but is accessible from terminals and desktops alike.
.PA
Global Access
*******
S07.GAL
*******
..pictureA:\NETWORK\S07.GAL,65535,49151,7,44,13,
Building upon the previous stage, the extended LAN enables multiple
local environments to be integrated as a single whole. Data that
was previously stored, and forwarded at a later more convenient
time, can now be interactively manipulated without geographical
constraints.
The total power of the networked systems is greatly enhanced as
more resources become available to the end users, and their
applications. Moves, additions, and changes to the networked system
necessitate a scalability of computing platforms. This in turn
requires easy portability of applications. The networked system
also needs to be carefully managed, to avoid bottlenecks and
unnecessary downtime.
The key enablers are now put in place: the communications
infrastructure consisting of bridges, routers, modems, and the
associated remote access points. Standardized application
programming interfaces ensures easy portability of applications to
alternative systems. A geographical and resource view of the
network is necessary to correctly balance the utilization of
resources in a dynamic environment.
Incremental developments during this phase emphasize additions of
bandwidth, increased network throughput, and additional
applications.
.PA
Global Access Environment
*******
S08.GAL
*******
..pictureA:\NETWORK\S08.GAL,65535,49151,7,44,13,
Seen from the end-user perspective, a few things have changed from
the previous stage. Interactive access to external data is now
possible. Domestic sales numbers can be accessed simultaneously
with international data. Online network management capabilities
provide possibilities to route network traffic in an controlled and
efficient manner.
A multitude of applications can be accessed and increased volumes
of data can be manipulated. Geography is no longer a restriction.
.PA
Resource Sharing
*******
S09.GAL
*******
..pictureA:\NETWORK\S09.GAL,65535,49151,7,44,13,
Physically, resources in a LAN environment are distributed over a
limited geographical area. A workgroup with individual PCs can
share output through nearby printers and plotters, commonly
accessible. Mini or mainframe servers provide centralized storage
of large volume data, as well as complex application programs
requiring external communications facilities. The network topology
determines the use of enablers such as media, access methods, and
physical network components. Transparent access is facilitated by
the introduction of common user interfaces.
.PA
Resource Sharing Environment
*******
S10.GAL
*******
..pictureA:\NETWORK\S10.GAL,65535,49151,7,44,13,
The common user interface will typically provide the capability of
displaying multiple applications simultaneously. A server may
provide access to an electronic mail application, storing and
forwarding messages that are displayed in one window on the PC
screen. Another window displays a spreadsheet application,
downloaded from a server seen as a networked drive. A third window
displays locally available data, such as sales statistics, or
production numbers stored on a local disk drive.
In a simple computing environment, these applications may handle
manual transfer of data, from local storage to spreadsheet
application, and further on to the mail system. In a more
developed environment, user agents may handle such a task on a
predetermined basis, requiring minimal end-user interaction.
.PA
Cooperating Applications
*******
S11.GAL
*******
..pictureA:\NETWORK\S11.GAL,65535,49151,7,44,13,
The functionality previously put in place, during stages one and
two, remain in place. Stage three enhances the capabilities of the
networked system through optimizing interdependence.
The final stage achieves the integration of servers. Data is
distributed across multiple servers, applications involve multiple
stage transactions and are likewise distributed across servers. To
route transactions and data, application logic is distributed in a
similar manner.
A truly open, cooperative computing environment has been achieved.
.PA
Cooperating Applications Environment
********
S12.GAL
*******
..pictureA:\NETWORK\S12.GAL,65535,49151,7,44,13,
To the end user, data and applications are now completely
transparently accessible. There is no need to know where data is
stored, how it is stored, or how to access the data. Even
manipulation of data is highly automated, especially in the case of
routine tasks.
The windowing environment remains. User agents handle most of the
application work. Distributed databases are seamlessly integrated
through equally distributed directory services. Remote procedure
calls, transaction processing monitors, and protocols handle the
application logic, independent of specific end-user commands.
.PA
Network Architecture
*******
S13.GAL
*******
..pictureA:\NETWORK\S13.GAL,65535,49151,7,44,13,
The enabling technology behind an open, cooperative computing
environment is best described as a modular architecture. Six
building blocks make up this model.
At the base, the communications infrastructure block defines the
available media, access methods, data link protocols, and the
corresponding routing algorithms.
Above the infrastructure, transport mechanisms handle tasks such as
end-to-end reliability, session establishment and termination,
syntax encoding, and the basics of applications integration.
The services block defines what functionality the network can
provide the applications; virtual terminal services, messaging, and
file services provide base level capabilities. Directory services
and interprocess communications protocols handle the more advanced
capabilities.
The management block interacts with the previous three blocks, to
provide fault detection, isolation, and correction, as well as
operations support mechanisms.
Surrounding these four blocks, and shielding the applications from
the underlying functionality, is the application programming
interface block. The common APIs enable standardized access to
each high-level service, as well as each underlying level of a
layered protocol architecture.
Finally, the applications block reside on top of the previously
mentioned components, portable from one platform environment to
another, thanks to the common APIs.
.PA
Communications Infrastructure
*******
S14.GAL
*******
..pictureA:\NETWORK\S14.GAL,65535,49151,7,44,13,
The basic components of a communications infrastructure need to
handle several tasks: local area networking requirements, wide area
network requirements, multiple speeds, access methods, and media. At
a minimum, LANs need to be able to support IEEE 802.3
non-deterministic access, and WANs need to support CCITT X.25 packet
switching and T1 leased line access.
In addition, most environments require high-speed networking, such
as fiber optic FDDI rings, and the associated links to LANs through
T3 leased lines.
Furthermore, connectivity to mainframe environments commonly
require SDLC support, as well as access to mainframe/PC
environments based on Token Ring principles.
ISDN, now prevalent in Europe and gaining in the U.S., will enable
applications such as integrated voice, fax, and electronic mail. An
example of this is HP's Applied Computerized Telephony solution
which, today, provides for integration of voice and data.
.PA
Transport Mechanisms
*******
S15.GAL
*******
..pictureA:\NETWORK\S15.GAL,65535,49151,7,44,13,
Two types of standard networking transport protocols exist; de jure
standards are based on adherence to internationally agreed upon
committee developments, de facto standards are based upon
individual developments submitted to the public domain, or on
market presence by dominant vendors.
Dividing the current offering of de jure and de facto standards
into three application areas we arrive at the following picture;
PC networks use de facto standards, for lack of equivalent de jure
standards. De facto standards are typically SPX/IP, for Novell
NetWare systems, XNS exists primarily in engineering applications
environments, and TCP/IP primarily exists in mixed PC and LAN
environments.
LANs typically use TCP/IP, or to some extent XNS as the dominant
multivendor de facto standards. For IBM environments, SNA is
obviously dominant. The de jure protocols are all based on Open
Systems Interconnection (OSI), as a rapidly emerging consensus
solution to network transport mechanisms.
In the wide area environment, TCP/IP and SNA make up the bulk of
de facto standards, again with an emerging presence of de jure
standards based on OSI.
.PA
Network Services
*******
S16.GAL
*******
..pictureA:\NETWORK\S16.GAL,65535,49151,7,44,13,
Network Services can be defined along similar lines, de jure and
de facto. An additional dimension will classify their complexity.
Starting with the basic services, virtual terminal capabilities can
be implemented in several ways, based on the choice of underlying
transport mechanisms.
If TCP/IP is used, Telnet is the service of choice. If OSI is used,
VTP is the corresponding service. For IBM environments, a 3270
emulator will provide the virtual terminal services.
Messaging and file services are divided along the same lines, as
are the more advanced services to the far right: directory services
and interprocess communications.
The picture details HP's current and near-term future
implementations of network services.
.PA
OpenView Network Management
*******
S17.GAL
*******
..pictureA:\NETWORK\S17.GAL,65535,49151,7,44,13,
OpenView is HP's strategy and solutions for distributed system and
network management. Managed objects, such as clients, servers,
instruments, peripherals, and network components feed events and
statistics through five functional areas of management. The
distributed management systems handles performance faults,
configuration, software distribution, accounting, and billing
issues. Various software modules, such as HP's GlancePlus,
OpenSpool, and NetLS, as well as ISV developed software for
configuration, accounting, and billing using HP's OpenView Network
Management tools issue commands and instructions back to the
managed objects of the networked system.
.PA
Application Programming Interfaces
*******
S18.GAL
*******
..pictureA:\NETWORK\S18.GAL,65535,49151,7,44,13,
APIs are standardized ways of accessing a service. Using an API,
the application integrator does not need to know the intrinsics of
a service. The API provides a set of common macro commands that an
application can use when accessing the service. The API will
translate the given command into a language acceptable to the
service.
By adhering to common standards, such as those agreed upon by the
members and followers of the X/Open organization's portability
guides (XPGs), applications may achieve a high degree of
portability. In other words, applications can be developed on
small, dedicated development engines, and later ported onto
production systems from various vendors and in various scales.
.PA
Network Directions
*******
S19.GAL
*******
..pictureA:\NETWORK\S19.GAL,65535,49151,7,44,13,
The Hewlett-Packard networking strategy for the future is based on
six pillars, adding to the capabilities of the current base of
technologies;
o Enhanced Communication Services provide integrated networking
services in key areas of functionality.
o Distributed Management Services handle events and statistical
information from managed objects in a networked system.
o Application Programming Interfaces shield service intrinsics from
end users and ensure portability of applications.
o High-Speed Access technologies enhance the functionality of the
communications infrastructure components.
o Software Development Tools aid developers of integrated networked
applications.
o Network Security protects networked systems from unauthorized
manipulation, and enhances reliability of the network itself.
.PA
Enhanced Communication Services
*******
S20.GAL
*******
..picturea:\NETWORK\S20.GAL,65535,49151,7,44,13,
The strategic direction for enhanced communication services can be
found in three areas; messaging, transaction processing, and the
Distributed Computing Environment.
Messaging services are provided by the X.400 store-and-forward
protocol. Enhanced addressing functionality is provided by the
X.500 distributed directory services protocol. On top of the X.400
standard, two information structures are added: Electronic Data
Interchange (EDI), based on the de jure EDIFACT definitions and
Office Document Architecture and Interchange Format (ODA/ODIF).
EDI is the standardized method of computer-to-computer exchange of
business documents like purchase orders and invoices. EDI replaces
paper transactions and considerably shortens the ordering, billing,
and payment cycles in a variety of corporate environments.
ODA provides standardized compound document transfer, such as
integrated text and graphics, and at a later stage, images.
Transaction processing services is the underlying networking
technology for a wide range of service industries. Standardized
transaction processing is intended for use with applications such
as automatic teller machines, airline reservations systems, hotel
reservations, and car rentals, to name just a few examples. The key
protocol is the ISO OSI TP, supplemented by remote database access
(RDA), remote procedure calls (RPC), and synchronization services
such as concurrent commit and recovery (CCR).
The local area network environment will be enhanced by the
implementation of the distributed computing environment (DCE),
where file services, directory services, and security enablers are
the key components. Engineering environments in particular will
benefit from the integrated technologies of DCE.
.PA
Distributed Management Services
*******
S21.GAL
*******
..pictureA:\NETWORK\S21.GAL,65535,49151,7,44,13,
Management can be structured into three levels, depending on the
view of the network. In its simplest form, management consists only
of interconnection management, providing a geographical view of the
network. The second step adds the possibility of managing resources
on the network. At the top, an applications view adds management of
the interaction between applications across the network.
For example, starting from the bottom; a networked printer fails to
print a bill of material, due to a failure in the modem connection.
Interconnect management detects the fault and sets off an alarm.
Information about the fault is passed on to the systems management
level. Here the fault is isolated, the output is spooled, for
example, re-routed to a nearby printer.
The applications management meanwhile informs the manufacturing
application of the delay in data delivery. Production is slowed
down in anticipation of new data, thus avoiding inventory build-up
at an intermediary processing stage.
Each management level in this model builds on the previous, until
applications finally interact to achieve the desired fault
correction, and restore normality to the network.
.PA
Application Programming Interfaces
*******
S22.GAL
*******
..pictureA:\NETWORK\S22.GAL,65535,49151,7,44,13,
Application programming interfaces shield the application
integrator from the intrinsics of the underlying software. APIs
also allow easier portability of application software, if
standardized APIs are used.
Starting in 1989, HP introduced service specific APIs, based on
agreements among vendors and users. For example, X.400 services
could be accessed through the vendor defined API-A.
In 1991, APIs were made available that could access not only
services, but also intermediate layers of the network protocol
stack. These APIs were typically part of the X/OPEN organization's
portability guides (XPGs). Still, each API, whether designed for
service access or intermediate layer access, was uniquely designed
for a particular service or protocol.
The next step is to introduce a unified access environment,
permitting access to any service or intermediate layer, but without
having to specify which. The unified API will direct the command to
the corresponding service or layer.
A first step in this direction is marked by the X/AP, an X/OPEN
defined API that covers multiple layers of an OSI protocol stack.
.PA
High-Speed Networking
*******
S23.GAL
*******
..pictureA:\NETWORK\S23.GAL,65535,49151,7,44,13,
Networking technologies can be defined by the possible throughput
of data and by the latency of data. Throughput is typically
measured in MByte/s; latency, the time between request and reply,
is measured in ms.
Current networking technology provides wide area networking
capabilities with sufficient throughput for store-and-forward
operations. Approximately one tenth of an MByte/s can be
transmitted, and the latency can be more than 1 second.
Existing local area networks provide better throughput, and better
latency. Throughout can be up to one Mbyte/s and the latency down
to 1 ms, adequate for most types of file transfer operations.
For the future, this networking environment must be enhanced. WANs
need to handle throughput speeds up to 100 MBytes/s, with a latency
of less than a second. LANs need approximately the same throughput
speeds, but with a latency coming down towards 0.1 ms.
These numbers will allow efficient communications, such as data
base access over wide area networks, supporting the transaction
processing environments of the future. Or, imaging and animation
taking place over high-speed local area networks.
.PA
Software Development Tools
*******
S24.GAL
*******
..pictureA:\NETWORK\S24.GAL,65535,49151,7,44,13,
Applications integration in an open, cooperative computing
environment can be a major undertaking. One way of reducing the
amount of work necessary, as well as allowing code to become
re-usable, is to provide a truly open development environment. HP
provides a STREAMS environment for its distributed networking
software. STREAMS makes the networking software completely modular,
and opens up the kernel software for application developers.
Thus, high-performance applications can be linked directly to
kernel software, and the re-usable code can drastically increase
programmer productivity.
HP also provides a wide range of software development tools,
originally used in internal developments, now productized and made
available to application developers. These tools include
functionality such as tracing and logging, auditing, performance
monitoring, and version checking.
In addition, a set of computer based training modules exist. These
are provided for self-paced studying, allowing knowledge of new
protocols and new concepts to become rapidly disseminated
throughout an organization. Some examples of this kind of tool
include the HP OTS/9000 CBT and the Introduction to X.500 directory
services CBT.
.PA
Security Services
*******
S25.GAL
*******
..picturea:\NETWORK\S25.GAL,65535,49151,7,44,13,
Today, security is primarily a concern of the operating system.
Guidelines for operating system security is defined in the so
called "Orange Book." Details of this type of security includes,
passwords, dial-back requests, and similar functions. A hierarchy
of security mechanisms are defined in three stages, C-, B-, and A-
level security, with A being the most secure. Military
requirements aside, C- and B-level security are usually deemed
adequate.
Network security is similarly defined by the so called "Red Book".
The same level definitions apply, although network security include
additional functionality such as traffic confidentiality, selective
routing of messages and the like.
In evolutionary terms, current HP networking provide C2-level
security, analogous with the C2 security level offered by the HP-UX
operating system. As of 1992 HP will be offering enhanced security
measures as defined by the B1-level specifications. Additional
security, as defined by the Kerberos specifications will be offered
beginning in 1993.
The final step will bring HP networking fully in line with the Open
Systems Foundation (OSF) proposals for C2/B1 security on the OSF/1
compliant systems of the future.
.PA
Support Services
*******
S26.GAL
*******
..pictureA:\NETWORK\S26.GAL,65535,49151,7,44,13,
HP has consistently been ranked #1 in support by Datapro surveys.
In 1991, HP won a special merit award for service and support for
midrange computers. Currently HP support services handle a
multitude of tasks, grouped into five broad categories:
planning and design of networked systems--pre-installation,
preparations, multivendor support of networked systems, on-going
maintenance, network operations support.
.PA
Summary
*******
S27.GAL
*******
..pictureA:\NETWORK\S27.GAL,65535,49151,7,44,13,
Cooperative Computing Through Open System is a wide ranging
concept. Some key components particularly are worth remembering,
however.
HP has several families of computers. These families provide a
range of scalable hardware platforms, from simple stand-alone
systems to mainframe-class multiprocessing systems. Open,
cooperative computing technologies are in many instances common
across the range of these platforms.
Network flexibility, in terms of moves, adds, and changes, is
provided by adherence to a consistent client/server architecture.
Multivendor interoperability is ensured through the use of standard
protocols, de facto as well as de jure.
Applications developed in this environment are easily portable from
one hardware platform to another, through the use of common,
standard application programming interfaces.
MIS productivity is enhanced by the integration of network and
systems management components, such as performance, fault,
configuration, software distribution, accounting, and billing
services, all under the HP OpenView umbrella.
In addition, HP provides a wide range of leading-edge support and
development tools, and has consistently been ranked #1 for its
worldwide support organization.
.PA